03. Technical Debt

Technical Debt:

Technical debts are gaps or issues in the internal quality of the product (i.e code base, test cases, etc) that exist either intentionally or unintentionally. Typical reason for these gaps to occur is that the product was launched on an expedited cycle to the market. These deficiencies accumulated over time make it harder to modify and expand the product in the future.

If you continue to ignore the technical debt and infrastructure updates, your product growth potential will be limited. When it is time to support a new feature, you may need to choose shortcuts that end up negatively affecting the efficiency and can cost the company more in the long-run.

Focus both on the short term and long term goals concurrently through a prioritized backlog for every sprint that keeps you on track to implement roadmap initiatives while addressing ongoing issues and requests as they arise.